Received: from relay2.UU.NET (relay2.UU.NET [192.48.96.7]) by keeper.albany.net (8.7.1/8.7.1) with ESMTP id QAA26526 for <dwarner@albany.net>; Fri, 19 Jan 1996 16:59:14 -0500 (EST)
Received: from garcia.com by relay2.UU.NET with SMTP
id QQzzfx03111; Fri, 19 Jan 1996 16:28:13 -0500 (EST)
Received: from (localhost) by garcia.com (5.x/SMI-SVR4)
id AA23568; Fri, 19 Jan 1996 16:28:16 -0500
Date: Fri, 19 Jan 1996 16:28:16 -0500
Errors-To: dwarner@albany.net
Message-Id: <Chameleon.960119162721.totoket@>
Errors-To: dwarner@albany.net
Reply-To: lightwave@garcia.com
Originator: lightwave@garcia.com
Sender: lightwave@garcia.com
Precedence: bulk
From: John DeNicola <totoket@callnet.com>
To: Multiple recipients of list <lightwave@garcia.com>
Subject: Newtek BBS News: Rev C - Win 95
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Status: RO
X-Status:
From: TEMPORAL ARTS -To-: CHUCK
Subj: Re: Where is LightWave PC Area: LightWave Su
In a message dated 01-10-96 12-07 Chuck writes:
C> The LightWave Intel patch files were posted here yesterday.
Chuck--
I'm trying really hard not to sound annoyed, so bear with me.
While the patch from Rev B to Rev C installed perfectly, the software
itself seems to have acquired MANY bugs in making the transition. Here's
few of the more obvious ones.
NOTE: All of my testing was done under Windows95, and, as I saw no note
saying that LW was officially Win95 compatible, that may be the cause of
most of these problems.
1. The most basic one seems to be that 4.0C has a broken interface under
Win95: the PopUp lists do not appear directly under the cursor;
they appear significantly ABOVE the cursor, and, while they are
still selectable, making any selection results in an "illegal
procedure" message and exits the program.
2. After this, I ran the version labeled 40b. Under this version, when
my system went into powersaver mode (blanks the monitor after 5 min,
shuts it off after 10), tapping the keyboard or jiggling the mouse
resulted in the same kind of message. This happened 3 times, and
only while the system was computing a shadow map (coincidence), so
I'm not sure if it's a general problem or one specific to shadow
maps.
These two items were enough to get me to reinstall Rev B from the original
CDROM. The extremely nice NewTek-AVI saver plugin works excellently
with Rev B, as do the other new plugins. I'm still using the old
HIIP plugin with IFF and TARGA loaders moved out of the loader
directory, and the system works fine.
Just thought I'd pass 'em on.
BTW, *is* LW 4.0C considered Win95 compatible at this time? I know there's
Win95 directory on the RevB CDROM, but after the AVI problem...well, you
now what I mean...
Thanks!
Don Cotnoir-Strong
Temporal Arts
905-351-7326
from: CHUCK -To-: TEMPORAL ARTS
subj: Re: Where is LightWave PC Area: LightWave Su
On Fri 12-Jan-1996 1:42 , Temporal Arts wrote:
A> 1. The most basic one seems to be that 4.0C has a broken interface under
A> Win95: the PopUp lists do not appear directly under the cursor;
A> they appear significantly ABOVE the cursor, and, while they are
A> still selectable, making any selection results in an "illegal
A> procedure" message and exits the program.
I confirm the positional shift on the popups, but we get no crashes here
such as you describe. Can you provide a detailed report - which popups (we
tried layout and Modeler both on Win95, on 90 and 100 MHz pentiums), etc.?
A> 2. After this, I ran the version labeled 40b. Under this version, when
A> my system went into powersaver mode (blanks the monitor after 5 min,
A> shuts it off after 10), tapping the keyboard or jiggling the mouse
A> resulted in the same kind of message. This happened 3 times, and
A> only while the system was computing a shadow map (coincidence), so
A> I'm not sure if it's a general problem or one specific to shadow
A> maps.
In general, don't let any TSR screensavers, etc, activate during rendering.
is really a bear about that.
A> BTW, *is* LW 4.0C considered Win95 compatible at this time? I know
A> there's a Win95 directory on the RevB CDROM, but A>
A> after the AVI problem...well, you know what I mean...
I don't think we've officially pronounced it Win95 compatible, but in
practice we are doing just as much test under 95 as NT these days, and when